System and methods for opportunistic migration of digital assets

ABSTRACT

An information handling system for migrating digital assets may include a storage medium configured to store information regarding digital assets to be migrated from a source system to a target system and a processor configured to determine a size of a digital asset to be migrated from the source system to the target system and select a mode of data transfer from the source system to the target system for the digital asset based on the size of the digital asset.

TECHNICAL FIELD

The present disclosure relates to the management of information handlingsystems. More specifically, embodiments of the disclosure provide asystem, method, and article of manufacture for opportunisticallymigrating entitled digital assets from a source system to a targetsystem.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

In recent years, it has become common for manufacturers to offerpurchasers the ability to order a system custom-configured to purchaserspecification. These custom-configured systems, which are often orderedonline, allow the purchaser to select the operating system (OS) of theirchoice along with a selection of software and other digital assets tomeet their individual needs. In some cases, the manufacturer maypreinstall the OS and the selected digital assets on the system prior todelivery. In addition, the system may be further personalized (e.g.,desktop themes and colors, etc.) as a service to the customer. Suchcustomizations and personalizations may be limited only by thecustomer's patience and willingness to define or describe their idealsystem.

However, there is currently no easy way for the purchaser to migratesoftware and other digital assets from an existing system to a newlypurchased system. As a result, the customer has to locate the originaldistribution media and license keys that came with the existing systemor were purchased later. In the event of downloaded digital assets, thepurchaser typically has to find back-up copies of the originaldownloaded files and emails that include the associated license keys. Ifthey are not located, or if they were lost due to a system failure suchas, for example, a crashed hard drive, the purchaser has to log-on tothe digital assets provider site, download the files again, and thenperform an authentication routine to receive the license keys via email.Moreover, it is not uncommon for users to misplace or forget their UserIDs and passwords. While methods exist to recover a log-in name andpassword, the process is inherently cumbersome, which may further delaythe user's recovery of the digital assets. As a result, these issues mayeither lengthen the time required to replace an existing system or causesystem owners to consider alternatives, such as thin client approaches(e.g., netbooks), cloud-based computing, or alternative operatingsystems. In view of the foregoing, there is a need for more easilymigrating digital assets from an existing system to a new system withoutrequiring the user to provide installation files and associated licensekeys.

Further complicating migrations of software and other digital assetsfrom a source system to a target system is that despite advancements inusage of a network cloud to configure information handling systemssystems and some software providers dictating changes to the wayinformation handling systems are deployed, the link to transfermigration data is often dependent on reliable internet connectivity.Unfortunately, many field configurations and deployments involveenvironments with inconsistent and unreliable internet connections,thus, making on-premise, system-to-system migrations still quitenecessary. Accordingly, systems and methods are desired for makingsystem-to-system migrations more efficient and less time-consuming.

SUMMARY

In accordance with the teachings of the present disclosure, thedisadvantages and problems associated with migration of digital assetshave been substantially reduced or eliminated.

In accordance with embodiments of the present disclosure, an informationhandling system for migrating digital assets may include a storagemedium configured to store information regarding digital assets to bemigrated from a source system to a target system and a processorconfigured to determine a size of a digital asset to be migrated fromthe source system to the target system and select a mode of datatransfer from the source system to the target system for the digitalasset based on the size of the digital asset.

In accordance with these and other embodiments of the presentdisclosure, a computer-implemented method for opportunistic migration ofdigital assets may include determining a size of a digital asset to bemigrated from a source system to a target system and selecting a mode ofdata transfer from the source system to the target system for thedigital asset based on the size of the digital asset.

In accordance with these and other embodiments of the presentdisclosure, an article of manufacture may include a computer readablemedium and computer-executable instructions carried on the computerreadable medium, the instructions readable by a processor, theinstructions, when read and executed, for causing the processor todetermine a size of a digital asset to be migrated from a source systemto a target system and select a mode of data transfer from the sourcesystem to the target system for the digital asset based on the size ofthe digital asset.

Technical advantages of the present disclosure may be readily apparentto one skilled in the art from the figures, description and claimsincluded herein. The objects and advantages of the embodiments will berealized and achieved at least by the elements, features, andcombinations particularly pointed out in the claims.

It is to be understood that both the foregoing general description andthe following detailed description are examples and explanatory and arenot restrictive of the claims set forth in this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments and advantagesthereof may be acquired by referring to the following description takenin conjunction with the accompanying drawings, in which like referencenumbers indicate like features, and wherein:

FIG. 1 illustrates a block diagram of an example information handlingsystem, in accordance with embodiments of the present disclosure;

FIG. 2 illustrates a block diagram of an example digital assetsentitlement system in accordance with components of the presentdisclosure;

FIGS. 3A-B illustrate block diagrams of an example unique systemidentifier that remains the same when one of its associated systemcomponent identifiers has been changed, in accordance with embodimentsof the present disclosure;

FIGS. 4A-B illustrate block diagrams of an example unique systemidentifier that is changed when one of its associated system componentidentifiers has been changed, in accordance with embodiments of thepresent disclosure;

FIG. 5 illustrates a block diagram of an example encrypted unique systemidentifier generated from a set of system component identifiers, inaccordance with embodiments of the present disclosure;

FIG. 6 illustrates a block diagram of an example unique systemidentifier decrypted from an encrypted unique system identifier, inaccordance with embodiments of the present disclosure;

FIGS. 7A-B illustrate a flow chart of an example method for performanceof digital asset entitlement operations, in accordance with embodimentsof the present disclosure;

FIG. 8 illustrates a flow chart of an example method for performance ofdigital assets migration operations, in accordance with embodiments ofthe present disclosure; and

FIG. 9 illustrates a flow chart of an example method for opportunisticmigration of digital assets, in accordance with embodiments of thepresent disclosure.

DETAILED DESCRIPTION

Preferred embodiments and their advantages are best understood byreference to FIGS. 1-9, wherein like numbers are used to indicate likeand corresponding parts.

For the purposes of this disclosure, an information handling system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, classify, process, transmit, receive, retrieve, originate,switch, store, display, manifest, detect, record, reproduce, handle, orutilize any form of information, intelligence, or data for business,scientific, control, entertainment, or other purposes. For example, aninformation handling system may be a personal computer, a personaldigital assistant (PDA), a consumer electronic device, a network storagedevice, or any other suitable device and may vary in size, shape,performance, functionality, and price. The information handling systemmay include memory, one or more processing resources such as a centralprocessing unit (CPU) or hardware or software control logic. Additionalcomponents of the information handling system may include one or morestorage devices, one or more communications ports for communicating withexternal devices as well as various input and output (I/O) devices, suchas a keyboard, a mouse, and a video display. The information handlingsystem may also include one or more buses operable to transmitcommunication between the various hardware components.

FIG. 1 illustrates a block diagram of an example information handlingsystem 100, in accordance with embodiments of the present disclosure.Information handling system 100 may include a CPU processor 102, I/Odevices 104, a hard drive or disk storage 106, a network port 110, amemory 112, and various other information handling resources 108, allcommunicatively coupled to each other via one or more buses 114. In someembodiments an information handling system identification similar tothat depicted in FIG. 1 may be used to implement one or more methodsand/or systems disclosed herein.

A processor 102 may include any system, device, or apparatus configuredto interpret and/or execute program instructions and/or process data,and may include, without limitation a microprocessor, microcontroller,digital signal processor (DSP), application specific integrated circuit(ASIC), or any other digital or analog circuitry configured to interpretand/or execute program instructions and/or process data. In someembodiments, processor 102 may interpret and/or execute programinstructions and/or process data stored in memory 112, hard drive 106,and/or another component of system 100.

An I/O device 104 may include any system, device, or apparatus fromwhich processor 102 may receive input or to which processor 102 maydeliver output. An I/O device may include a display, a keyboard, amouse, other I/O devices, and/or associated controllers.

Hard drive 106 may include computer-readable media (e.g., magneticstorage media, optical storage media, opto-magnetic storage media,and/or other type of rotating storage media, flash memory, and/or othertype of solid state storage media) and may be generally operable tostore data and/or programs (e.g., one or more operating systems and/orone or more application programs). Although FIG. 1 depicts informationhandling system 100 as including one hard drive 106, informationhandling system 100 may include any suitable number of hard drives 106.

Network port 110 may include any suitable system, apparatus, or deviceoperable to serve as an interface between information handling system100 and a network. Network port 110 may enable information handlingsystem 102 to communicate over such network using any suitabletransmission protocol and/or standard, including without limitationFibre Channel, Frame Relay, Asynchronous Transfer Mode (ATM), InternetProtocol (IP), other packet-based protocol, small computer systeminterface (SCSI), Internet SCSI (iSCSI), Serial Attached SCSI (SAS) orany other transport that operates with the SCSI protocol, advancedtechnology attachment (ATA), serial ATA (SATA), advanced technologyattachment packet interface (ATAPI), serial storage architecture (SSA),integrated drive electronics (IDE), and/or any combination thereof.

Memory 112 may be communicatively coupled to processor 102 and mayinclude any system, device, or apparatus configured to retain programinstructions and/or data for a period of time (e.g., computer-readablemedia). Memory 112 may include random access memory (RAM), electricallyerasable programmable read-only memory (EEPROM), a Personal ComputerMemory Card International Association (PCMCIA) card, flash memory,magnetic storage, opto-magnetic storage, or any suitable selectionand/or array of volatile or non-volatile memory that retains data afterpower to information handling system 100 is turned off. Although FIG. 1depicts information handling system 100 as including one memory 112,information handling system 100 may include any suitable number ofmemories 112.

Other information handling resources 108 may include any componentsystems, devices, or apparatuses of an information handling system 100,including without limitation processors, buses, memories, I/O devicesand/or interfaces, storage resources, network interfaces, motherboards,electro-mechanical devices (e.g., fans), displays, and power supplies.

The one or more buses 114 may comprise any suitable collection ofsystems, devices, or apparatuses configured to transfer data betweenvarious components of information handling system 100. For example, oneor more buses 114 may include a serial advanced technology attachment(SATA) bus, a Peripheral Component Interconnect (PCI)/PCMCIA bus,Universal Serial Bus (USB), an SCSI bus, FireWire (IEEE 1394) bus,InfiniBand bus, any other suitable bus, or any combination of theforegoing.

FIG. 2 illustrates a block diagram of an example digital assetsentitlement system 218, in accordance with embodiments of the presentdisclosure. In some embodiments, digital assets entitlement system 218may be implemented for managing the entitlement of a system 204 toprocess a digital asset 246. In these and other embodiments, digitalassets entitlement system 218 may be implemented on one or more servers210, which may be commercially coupled to a network 252. In variousembodiments, network 252 may comprise a public network, for example theInternet, a physical private network, a virtual private network (VPN),or any combination thereof. As shown in FIG. 2, digital assetsentitlement system 218 may include a user service and support module220, a digital fulfillment module 222, and a system identification andsecurity module 224. Digital assets entitlement system 218 may likewisecomprise a personalization module 226, an entitlement module 228, asales integration module 230, and a manufacturing integration module232. In addition, digital assets entitlement system 218 may beconfigured to access a digital assets data repository 212, anentitlement data repository 214, and a system identifier (ID) datarepository 216, each of which may be implemented on one or more servers210 communicatively coupled to network 252.

As used herein, a digital asset 246 refers to any digital asset, forexample, a software application, a deliverable or performable service,music, video, software activation key, personalization instructions,files, etc. that are digitally deliverable either wholly or partially.As likewise used herein, a digital assets entitlement may refer to theassociation of a predetermined digital asset 246 with a target system204. In various embodiments, an entitlement record may include thedigital assets entitlement data (e.g., license information, etc.) thatallows digital asset 246 to be processed by a target system 204identified by a corresponding unique system identifier 206. In these andother embodiments, the entitlement record may be processed byentitlement module 228 and stored in entitlement data repository 214.Likewise, as used herein, a system 204 may comprise an informationhandling system (e.g., a personal computer, a laptop computer, a tabletcomputer, a PDA, a mobile telephone, or any other suitable device)operable to store a unique system ID 206, perform digital assetentitlement operations with a personalization agent, and operable toestablish an online session with digital assets entitlement system 218via network 252.

In some embodiments, digital assets entitlement and systempersonalization operations may be performed by a user 202, in either aphysical environment or an online environment. A user 202 may comprise asystem purchaser, enterprise administrator, information technologist, oranother suitable person. As an example, a physical environment maycomprise a retailer 240 operating a physical point-of-sale (POS) system242. As another example, an online environment may comprise a systemmanufacturer 234, after-point-of-sale (APOS) vendor 236, or digitalassets vendor 238, that respectively accepts online orders for systemsor digital assets via network 252.

If the digital assets entitlement and system personalization operationsare performed in an online environment, then user 202 may decide whetherto purchase a custom-configured or pre-configured system 204. If thesystem 204 is to be pre-configured, then it may be selected for onlinepurchase by the user 202 and its unique system identifier 206 may bedetermined. In some embodiments, the unique system identifier 206 may bestored in the basic input/output system (BIOS) of the pre-configuredsystem 204. However, if the system 204 is to be custom-configured, thenit may be custom-configured for online purchase by user 202. Oncemanufactured by system manufacturer 234, a unique system identifier maybe generated as described in greater detail herein.

In various embodiments, manufacturing integration module 232 maycoordinate the custom configuration of the system 204 with digitalassets entitlement system 218. Likewise, system identification andsecurity module 224 may coordinate the generation of unique systemidentifier 206 and its storage in the repository of system identifierdata 216. User 202 may then select a digital asset 246 for onlinepurchase, followed by selecting personalization options for thepre-configured or custom-configured system 204. In various embodiments,the personalization module 226 coordinates the selection ofpersonalization options with digital assets entitlement system 218. Asused herein, a system personalization option refers to any feature,capability, or function that may be applied to a target system 204. Asan example, a personal computer desktop wallpaper or user interfaceoptions (e.g., a “classic” interface) are personalization options.

However, if the digital assets entitlement and system personalizationoperations are performed in a physical environment, then user 202 mayselect a pre-configured system 204 and physical representations ofdigital assets 246 to be purchased. In various embodiments, the digitalasset 246 may be physically represented as images and/or text on a cardor a package, yet the digital assets themselves may not be includedwithin the card or package. User 202 may then select systempersonalization options for the pre-configured system 204. In variousembodiments, the system personalization options may likewise bephysically represented as images and/or text on a card or a package.

The digital assets product identifier (ID) may then be scanned with ascanner 244 from its corresponding physical representation, followed byscanning its corresponding digital assets activation key or otherentitlement data. In various embodiments, it is not necessary to scanthe digital assets activation key or other entitlement data as it isprovided by digital assets entitlement system 218 during digital assetentitlement operations described in greater detail herein. Data relatedto the previously selected personalization options may then likewise bescanned, followed by determining unique system identifier 206 ofpre-configured system 204. In various embodiments, the digital assetsproduct ID, its associated activation key or entitlement data, thepersonalization option data, and the unique system identifier may berepresented by a bar code 248 or other indicia on a card or physicalpackage. In various other embodiments, the digital assets product ID,its associated activation key or entitlement data, the personalizationoption data, and the unique system identifier may be stored in a radiofrequency identifier (RFID) 250 tag affixed to the physicalrepresentation of the digital asset. Those of skill in the art mayappreciate that many such embodiments are possible and that theforegoing is not intended to limit the spirit, scope, or intent of thedisclosure.

A purchase transaction for the custom-configured or pre-configuredsystem 204 and any associated digital assets 246 and personalizationoptions may then be completed. In various embodiments, the processing ofthe purchase transaction may be performed by the sales integrationmodule 230. In these and other embodiments, the financial proceeds ofthe purchase transaction may be settled between multiple parties. Forexample, a system manufacturer 234 may receive a portion of the purchasetransaction corresponding to the cost of the system 204. One or moredigital assets vendors 238 may likewise receive a proportionate share ofthe purchase transaction corresponding to the digital asset 246 theyrespectively provide.

Digital asset entitlement operations, as described in greater detailherein, may then be performed by digital assets entitlement system 218to bind the digital assets 246, the personalization options, and theirrespective digital assets entitlement data to unique system identifier206 of target system 204. The resulting bound data, including dataassociated with the digital assets (e.g., installation files, etc.) maythen be stored in the repository of entitlement data 214 and purchasedsystem 204 may then be delivered to user 202 or another persondesignated by user 202. In various embodiments, entitlement module 228may generate, and then process, the digital assets entitlement data, anduser service and support module 220 may coordinate the delivery ofsystem 204 to user 202 or another person designated by user 202.

Standard operating system (OS) out-of-the-box-experience (OOBE) orhypervisor boot operations may be performed on the system 204, followedby loading a personalization agent 208. In various embodiments, thepersonalization agent 208 has a unique identifier that may be associatedwith one or more unique system component identifiers. In someembodiments, the unique identifier of the personalization agent may beuniquely associated with the current unique system identifier 206associated with the system 204. In other embodiments, a portion of thepersonalization agent 208 may be delivered to the system 204 in anencrypted form and may then be decrypted prior to being loaded on thesystem 204. In these embodiments, the primary system identifier (e.g.,service tag number, serial number, etc.) may be used as a decryption keyto decrypt the personalization agent 208.

In these and other embodiments, secondary system identifiers may bestored on system 204 (e.g., in the BIOS, in flash memory, on a harddisk, etc.) as well as in digital assets entitlement system 218. Inthese and other embodiments, digital assets entitlement system 218 mayuse the secondary system identifiers to encrypt a portion ofpersonalization agent 208 before it is downloaded to system 204. Oncedownloaded, the unencrypted portion of personalization agent 208 may usethe secondary system identifiers stored on system 204 to decrypt theencrypted portion of personalization agent 208. In some embodiments, thesecondary system identifiers may likewise be encrypted and may first bedecrypted before they are used to decrypt the encrypted portion ofpersonalization agent 208. In other embodiments, the secondary systemidentifiers may be stored in a Trusted Platform Module (TPM). Skilledpractitioners of the art may appreciate that many such embodiments arepossible and the foregoing is not intended to limit the spirit, scope,or intent of the disclosure.

Personalization agent 208 may query target system 204 for its uniquesystem identifier 206. In various embodiments, unique system identifier206 associated with system 204 may be stored in the target system'sBIOS, flash memory, a hard disk, and/or other memory device.Personalization agent 208 may then automatically establish acommunication session with digital assets entitlement system 218 and useunique system identifier 206 to authenticate system 204. Unique systemidentifier 206 may then be used by the personalization agent 208 todetermine entitled digital assets and personalization optionscorresponding to the unique system identifier 206.

Once determined, the corresponding personalization options and digitalassets 246, along with their associated digital assets entitlement data,may be respectively downloaded to target system 204 from the repositoryof digital assets 212 and the repository of entitlement data 214. Insome embodiments, the personalization options and digital assets 246,along with their associated digital assets entitlement data 214, may bedownloaded from a single digital assets entitlement system server 210 onnetwork 252. In other embodiments, the personalization options anddigital assets 246 may be downloaded from one or more servers 210 onnetwork 252. In yet other embodiments, the personalization options,digital assets 246, and associated digital assets entitlement data 214may be respectively downloaded from a plurality of servers 210 onnetwork 252. As an example, a first digital asset 246 may be provided bysystem manufacturer 234 and a second digital asset 246 may be providedby a digital assets vendor 238. Likewise, a plurality of digital assets246 may be provided by a corresponding plurality of digital assetvendors 238. Skilled practitioners of the art may appreciate that manysuch embodiments and examples are possible and the foregoing is notintended to limit the spirit, scope, or intent of the disclosure.

In various embodiments, digital assets entitlement system 218 may managethe respective location of the personalization options, digital assets246, and associated digital assets entitlement data 214 to initiate itsprovision. Once downloaded, personalization agent 208 may use digitalassets entitlement data 214 to install digital assets 246 andpersonalization options on system 204. Thereafter, user 202 or anotherperson may decide to perform an APOS purchase of digital asset 246. Asused herein, an APOS purchase of digital assets may refer to anypurchase of digital asset 246 made after the initial online or physicalpurchase of system 204. In various embodiments, the APOS purchase of adigital asset 246 may be performed in a physical, online, or enterprisepoint-of-sale environment. If the APOS purchase is performed in anonline environment, for example from APOS vendor 236, then user 202 oranother person may select a digital asset 246 for online purchase.Personalization agent 208 may then determine unique system identifier206 of system 204. An APOS purchase transaction may then be performedfor purchase of the selected digital asset 246. However, if the APOSpurchase is performed in a physical environment, then the user 202 oranother person may select a physical representation of a digital asset246 to be purchased. The digital assets product ID may then be scannedfrom its corresponding physical representation, followed by scanning itscorresponding digital assets activation key or other entitlement data.

Digital asset entitlement operations, as described in greater detailherein, may then be performed by digital assets entitlement system 218to bind digital assets 246 and their respective digital assetsentitlement data 214 associated with the APOS purchase to unique systemidentifier 206 of target system 204. The resulting bound data, includingdata associated with the digital assets (e.g., installation files, etc.)may then be stored, as described in greater detail herein, in digitalassets entitlement system 218. Personalization agent 208, as likewisedescribed in greater detail herein, then automatically establishes acommunicative session with digital assets entitlement system 218, andmay download the purchased digital assets 246 and their associateddigital assets entitlement data 214. Once downloaded, personalizationagent 208 may then use the associated digital assets entitlement data214 to install the downloaded digital asset 246 on system 204.

FIGS. 3A-B illustrate a block diagram of an example original uniquesystem identifier 320 that remains the same when one of its associatedsystem component identifiers has been changed, in accordance withembodiments of the present disclosure. As shown in FIG. 3A, an originalunique system identifier 320 may be generated from a plurality of uniquesystem component identifiers 302, which correspond to a plurality ofsystem components included in a target system 204. As likewise shown inFIG. 3A, unique system component identifiers 302 may comprise a ModelNumber 304 ‘SA310J43’, a Serial Number 306, sometimes referred to as aservice tag number or a primary system identifier, ‘SEM5239923875’, aFactory ID 308 ‘AUS’, and a Manufacture Date 310 ‘111909’.

Unique system component identifiers 302 may likewise comprise anOriginal Motherboard ID 314 ‘19374WS238017BH’, a Processor ID 316‘92348430-432919237’, a Hard Drive ID 318 ‘L83747HJ3672’, etc.

As described in greater detail herein, once generated, original uniquesystem identifier 320 may be associated, such as, for example, through abinding operation, with predetermined digital assets 332 to generate adigital assets entitlement 330. As likewise described in greater detailherein, digital assets entitlement 330 entitles a target system 204,which may be associated with the original unique system identifier 320,to process the digital assets 332. However, it is not uncommon forsystem components to be replaced due to failure, erratic performance,becoming outmoded, or for other reasons. It will be appreciated that theentitlement 330 between original unique system identifier 320 anddigital assets 332 may be compromised as a result of such a replacement.For example, as illustrated in FIG. 3B, the Original Motherboard ID 314‘19374WS238017BH’ may be replaced with a New Motherboard ID 334‘56812FR853945PL’. However, in such case the original unique systemidentifier 320 may remain unchanged.

In various embodiments, extract, transform, and load (ETL) and otherdatabase operations may be performed to manage the integrity of therelationship between original unique system identifier 320 and theplurality of unique system component identifiers 302. As an example,Original Motherboard ID 314 ‘19374WS238017BH’ may remain as a subset oforiginal unique system identifier 320, even though it may have beendeactivated or invalidated as a unique system component identifier 302.However, in these and other embodiments, relational database operationsknown to those of skill in the art may be applied to maintain therelationship between original unique system identifier 320, New OriginalMotherboard ID 334 ‘56812FR853945PL’, and unchanged unique systemcomponent identifiers 302. Accordingly, the integrity of entitlement 330between original unique system identifier 320 and digital assets 332 maybe perpetuated. It may be appreciated by skilled practitioners of theart that many such embodiments are possible and the foregoing is notintended to limit the spirit, scope, or intent of the disclosure.

FIGS. 4A-B illustrate a block diagram of an example unique systemidentifier 320 that is changed when one of its associated systemcomponent identifiers has been changed, in accordance with embodimentsof the present disclosure. As shown in FIG. 4A, an original uniquesystem identifier 320 may be generated from a plurality of unique systemcomponent identifiers 302, which correspond to a plurality of systemcomponents included in a target system 204. As likewise shown in FIG.3A, unique system component identifiers 302 may comprise Model Number304 ‘SA310J43’, Serial Number 306, sometimes referred to as a servicetag number or a primary system identifier, ‘SEM5239923875’, Factory ID308 ‘AUS’, and Manufacture Date 310 ‘111909’. Unique system componentidentifiers 302 may likewise comprise Original Motherboard ID 314‘19374WS238017BH’, Processor ID 316 ‘92348430-432919237’, Hard Drive ID318 183747HJ3672′, etc.

As described in greater detail herein, once generated, original uniquesystem identifier 320 may be associated, such as, for example, through abinding operation, with predetermined digital assets 332 to generate adigital assets entitlement 330. As likewise described in greater detailherein, digital assets entitlement 330 entitles a target system 204,which may be associated with original unique system identifier 320, toprocess digital assets 332. However, it is not uncommon for systemcomponents to be replaced due to failure, erratic performance, becomingoutmoded, or for other reasons. It will be appreciated that entitlement330 between the original unique system identifier 320 and digital assets332 may be compromised as a result of such a replacement. For example,as illustrated in FIG. 4B, Original Motherboard ID 314 ‘19374WS238017BH’may be replaced with New Motherboard ID 334 ‘56812FR853945PL’. Asresult, a new unique system identifier 420 may be generated, which maybe a concatenation of the plurality of unique system componentidentifiers 402, including New Original Motherboard ID 334‘56812FR853945PL’ as a subset.

In various embodiments, a first set of operations may be performed toremove entitlement 330 between original unique system identifier 320 anddigital assets 332. A second set of operations may then be performed toassociate new unique system identifier 420 with digital assets 332 togenerate a new entitlement 430. In these and other embodiments, originalunique system identifier 320 may then be invalidated. Accordingly, theintegrity of original entitlement 330 between original unique systemidentifier 320 and digital assets 332 may be perpetuated by newentitlement 430 between new unique system identifier 420 and digitalassets 332. Skilled practitioners of the art may appreciate that manysuch embodiments are possible and the foregoing is not intended to limitthe spirit, scope, or intent of the disclosure.

FIG. 5 illustrates a block diagram of an example encrypted unique systemidentifier 528 generated from a set of system component identifiers, inaccordance with embodiments of the present disclosure. In theseembodiments, a source unique system identifier 520 may be generated froma plurality of original unique system component identifiers 502, whichmay correspond to a plurality of system components included in a targetsystem 204. As shown in FIG. 5, original unique system componentidentifiers 502 may comprise Model Number 304 ‘SA310J43’, Serial Number306, sometimes referred to as a service tag number or a primary systemidentifier, ‘SEM5239923875’, Factory ID 308 ‘AUS’, Timestamp Date 510‘111909’, and Timestamp Time 512 ‘14:27:26:34’. Original unique systemcomponent identifiers 502 may likewise comprise Original Motherboard ID314 ‘19374WS238017BH’, Processor ID 316 ‘92348430-432919237’, Hard DriveID 318 183747HJ3672′, etc.

An encryption operation 524 may then be performed on source uniquesystem identifier 520 to generate original encrypted unique systemidentifier 528. In various embodiments, the encryption operation maycomprise the use of a private key, a public key, key pairs, or anycombination of keys and cryptographic operations such as implemented ina public key infrastructure (PKI), for example. As an example, theoriginal encrypted unique system identifier 528 may be generated using aprivate key associated with the manufacturer of the system and a publickey associated with the system itself. In some embodiments, theTimestamp Date 510 ‘111909’ and the Timestamp Time 512 ‘14:27:26:34’ maylikewise be used to generate the encrypted unique system identifier 528.Skilled practitioners of the art may be familiar with such cryptographicoperations and may appreciate that many such embodiments are possibleand that the foregoing is not intended to limit the spirit, scope, orintent of the disclosure.

As described in greater detail herein, once generated, originalencrypted unique system identifier 528 may be associated, such as, forexample, through a binding operation, with predetermined digital assets332 to generate a digital assets entitlement 530. As likewise describedin greater detail herein, digital assets entitlement 530 may entitle atarget system 204, which may be associated with original encryptedunique system identifier 528, to process digital assets 332.

FIG. 6 illustrates a block diagram of an example unique systemidentifier decrypted from an encrypted unique system identifier 622, inaccordance with embodiments of the present disclosure. It is notuncommon for system components to be replaced due to failure, erraticperformance, becoming outmoded, or for other reasons. However, thereplaced system component will typically have a different unique systemcomponent identifier. As a result, the entitlement association between aunique system identifier and predetermined digital assets may becompromised as a result of such a replacement, which in turn may preventtarget system 204 from processing the digital assets 246.

In various embodiments, the unique system component identifier of thereplacement system component may be unknown until it is replaced in thetarget system 204. In these and other embodiments, the system componentmay be replaced in the target system 204, the target system 204 may thenbe initiated (e.g., booted), and an inventory of unique system componentidentifiers may be performed. In some embodiments, one or more uniquesystem component identifiers, for example a serial number or servicetag, may be visible and may be visually inventoried. In otherembodiments, one or more unique system component identifiers, forexample a motherboard, processor, or hard drive serial number, may notbe visible and may be automatically inventoried.

As shown in FIG. 6, a new source unique system identifier 650 may begenerated from the inventoried unique system component identifiers. Insome embodiments, a time stamp date and a time stamp time may becomponents of new source unique system identifier 650. In theseembodiments, the time stamp date and a time stamp time may be used tovalidate the authenticity of new source unique system identifier 650. Asan example, the provider of the replacement part may have stipulatedthat the replacement part be replaced on Nov. 12, 2009, between 8:00 AMand 6:00 PM. Accordingly, a time stamp date of Nov. 12, 2009 and a timestamp time of 16:33:42:05 may provide validation that the replacementpart was replaced within the specified date and time interval.

An encryption operation 652 may then be performed on new source uniquesystem identifier 650 to generate a new encrypted unique systemidentifier 628. As an example, the encryption operation may be performedusing a private key associated with the target system and a public keyassociated with the provider of the replacement system component. Thenew encrypted unique system identifier 628 may then be communicated todigital assets entitlement system 218, which may in turn perform adecryption operation 626 to generate a decrypted unique systemidentifier 622.

As likewise shown in FIG. 6, ETL and other database operations 634 maybe performed on the decrypted unique system identifier 622 to generatenew unique system component identifiers 602. As shown in FIG. 6, the newunique system component identifiers may now comprise Model Number 304‘SA310J43, Serial Number 306, ‘SEM5239923875’, Factory ID 308 ‘AUS’,Timestamp Date 610 ‘112009’, and Timestamp Time 612 ‘16:33:42:05’. Newunique system component identifiers 602 may likewise comprise NewMotherboard ID 314 ‘56812FR853945PL’, Processor ID 316‘92348430-432919237’, Hard Drive ID 318 ‘L83747HJ3672’, etc. In someembodiments, Timestamp Date 610 and Timestamp Time 612 may be comparedto previously authorized timestamp date and timestamp times to validatethe authenticity of new unique system component identifiers 602 andtheir corresponding decrypted unique system identifier 622. In these andother embodiments, if the decrypted unique system identifier 622 isvalidated, then a first set of operations may be performed to removeentitlement 330 between the original encrypted unique system identifierand digital assets 332. A second set of operations may then be performedto associate new encrypted unique system identifier 628 with digitalassets 332 to generate new entitlement 630. Accordingly, the integrityof the original entitlement between the original encrypted unique systemidentifier and digital assets 332 may be perpetuated by new entitlement630 between new encrypted unique system identifier 628 and digitalassets 332.

In various other embodiments, the provider of the replacement systemcomponent may be able to determine its associated unique systemcomponent identifier. In some embodiments, the unique system componentidentifier may be known in advance. In other embodiments, the uniquesystem component identifier may be one of a pool of, or a range of,possible unique system component identifiers set aside for replacementpurposes. As described in greater detail herein, a new source uniqueidentifier may be generated, using the unique system componentidentifier of the component to be replaced. Once the new source uniqueidentifier is generated, the unique system component identifier of thereplaced system component may be invalidated. In these and otherembodiments, the system component may be replaced in the target system,the target system may then be initiated (e.g., booted), and an inventoryof unique system component identifiers may be performed. In someembodiments, one or more unique system component identifiers, forexample a serial number or service tag, may be visible and may bevisually inventoried. In other embodiments, one or more unique systemcomponent identifiers, for example a motherboard, processor, or harddrive serial number, may not be visible and may be automaticallyinventoried.

As shown in FIG. 6, a new source unique system identifier 650 may begenerated from the inventoried unique system component identifiers. Insome embodiments, a time stamp date and a time stamp time may becomponents of new source unique system identifier 650. In theseembodiments, the time stamp date and a time stamp time may be used tovalidate the authenticity of new source unique system identifier 650. Anencryption operation 652 may then be performed on new source uniquesystem identifier 650 to generate new encrypted unique system identifier628. As an example, the encryption operation may be performed using aprivate key associated with the target system and a public keyassociated with the provider of the replacement system component. Thenew encrypted unique system identifier 628 may then be communicated to adigital assets entitlement system, which in turn may perform adecryption operation 626 to generate a decrypted unique systemidentifier 622.

Comparison operations 654 may then be performed between the new sourceunique system identifier and decrypted unique system identifier 622. Ifcomparison operations 654 are successful, then a first set of operationsmay be performed to remove the entitlement 330 between the originalencrypted unique system identifier and digital assets 332. A second setof operations may then be performed to associate new encrypted uniquesystem identifier 628 with digital assets 332 to generate a newentitlement 630. Accordingly, the integrity of the original entitlementbetween the original encrypted unique system identifier and digitalassets 332 may be perpetuated by the new entitlement 630 between the newencrypted unique system identifier 628 and the digital assets 332.Skilled practitioners of the art may appreciate that many suchembodiments are possible and the foregoing is not intended to limit thespirit, scope, or intent of the disclosure.

FIGS. 7A-B illustrate a flow chart of an example method 700 forperformance of digital asset entitlement operations, in accordance withembodiments of the present disclosure. According to certain embodiments,method 700 may begin at step 702. As noted above, teachings of thepresent disclosure may be implemented in a variety of configurations ofsystem 200. As such, the preferred initialization point for method 700and the order of the steps 702-734 comprising method 700 may depend onthe implementation chosen.

In method 700, digital asset entitlement operations may be started instep 702, followed by the selection of a target system in step 704 fordigital assets entitlement. The unique system identifier of the targetsystem, as described in greater detail herein, may be determined in step706, followed by a determination being made in step 708 whether a devicerecord has been established for the target system. If not, then thedevice record may be generated in step 710. As used herein, a devicerecord may refer to a data record comprising data related to a systemwhich will receive an entitlement to process associated digital assets.In various embodiments, the unique system identifier of the targetsystem may be stored in the device record. In various embodiments, otherrecords may be associated with the device record to further describe thesystem, such as, for example, its model, type, make, internalidentifiers, etc.

Once the device record has been generated, or if it is determined instep 708 that it has already been established, then a determination maybe made in step 712 whether an account record has been established for auser. If not, then the account record may be generated for the user instep 714. As used herein, an account record may refer to a data recordcomprising data related to the association of multiple devices orsystems to one or more entities. In various embodiments, the entity maybe a single individual or a group of individuals. As an example, theentity may be a household with multiple PCs, a small business withseveral employees, a large corporation with many employees, etc. Otherrecords may be attached to the account to further describe the accountholder, payment information related to the account, etc. Accounts mayfurther be broken down or organized into sub-accounts as needed (e.g.,to describe departments within an enterprise). In various embodiments, auser may be associated with a single device or system or multipledevices or systems in the account record. Conversely, a group of usersmay be associated with a single device or system or multiple devices inthe account record. Further, more groups of individual users maylikewise be associated with groups of individual devices or systems.Those of skill in the art may appreciate that many such associations arepossible and the foregoing is not intended to limit the spirit, scope,or intent of the disclosure. Once the account record has been generated,or if it is determined in step 712 that it has already been established,then a determination may be made in step 716 whether the account recordmay be associated with the target system. If not, then the accountrecord may be associated with the target system in step 718.

Once the account record has been associated with the target system, orif it is determined in step 716 that it has already been associated,then a target list of digital assets may be presented in step 720 forentitlement. A determination may then be made in step 722 whether togenerate an entitlement for a digital asset. If not, then adetermination may be made in step 732 whether to continue digital assetentitlement operations. If so, then the process may be continued,proceeding with step 704. Otherwise digital asset entitlement operationsmay be ended in step 734. However, if it is determined in step 722 togenerate an entitlement for a digital asset, then a target digital assetmay be selected in step 724. A digital assets entitlement may then begenerated in step 726 by performing operations to associate the selecteddigital asset's corresponding license record with the aforementioneddevice record, account record, and/or other predetermined records. Theresulting digital assets entitlement association may then be added tothe entitlement record in step 728. A determination may then be made instep 730 whether to generate another digital assets entitlement. If so,the process may be continued, proceeding with step 724. Otherwise, adetermination may be made in step 732 whether to continue digital assetentitlement operations. If so, then the process may be continued,proceeding with step 704. Otherwise digital asset entitlement operationsmay be ended in step 734.

Although FIGS. 7A and 7B disclose a particular number of steps to betaken with respect to method 700, method 700 may be executed withgreater or lesser steps than those depicted in FIGS. 7A and 7B. Inaddition, although FIGS. 7A and 7B disclose a certain order of steps tobe taken with respect to method 700, the steps comprising method 700 maybe completed in any suitable order.

Method 700 may be implemented using information handling system 100,system 200, components thereof, and/or any other system operable toimplement method 700. In certain embodiments, method 700 may beimplemented partially or fully in software and/or firmware embodied incomputer-readable media.

FIG. 8 illustrates a flow chart of an example method 800 for theperformance of digital assets migration operations, in accordance withembodiments of the present disclosure. According to certain embodiments,method 800 may begin at step 802. As noted above, teachings of thepresent disclosure may be implemented in a variety of configurations ofsystem 200. As such, the preferred initialization point for method 800and the order of the steps 802-830 comprising method 800 may depend onthe implementation chosen.

In method 800, digital assets migration operations may begin in step802. A determination may be made in step 804 whether a personalizationagent is loaded on the source system. If it is determined in step 804that a personalization agent is not loaded on the source system, then itmay be loaded in step 806. In either case, the personalization agent mayquery the target system to determine its unique system identifier instep 808. After the system identifier is determined in step 808,inventory operations may then be performed in step 810 by thepersonalization agent to inventory digital assets and any associateddigital assets entitlement data installed on the source system.

The personalization agent may then automatically establish acommunicative session with the digital assets entitlement system in step812 and use the unique system identifier to authenticate the sourcesystem and upload the inventoried digital assets and digital assetsentitlement data associated with the source system. The digital assetsentitlement system may then perform comparison operations in step 814between the digital assets and the digital assets entitlement datarespectively corresponding to the source system's and the targetsystem's unique system identifiers. A determination may then be made instep 816 if all of the inventoried digital assets and digital assetsentitlement data associated with the source system's unique systemidentifier is now associated with the target system's unique systemidentifier.

If not, then the digital assets and digital assets entitlement data notassociated with the unique system identifier of the target system may bedetermined in step 818. The user may then be prompted in step 820 toprovide any missing license keys, or other digital assets entitlementdata, associated with inventoried digital assets that are not currentlyassociated with the target system's unique system identifier. The usermay then provide the requested digital assets license keys or othermissing digital assets entitlement data to the digital assetsentitlement system in step 822.

Digital assets entitlement data may then be generated in step 824 bybinding the digital assets and their associated activated activation keyor other digital assets entitlement data to the unique system identifierof the source system. The bound data may then be stored in the digitalassets entitlement system in step 826. The entitlement of the digitalassets is then migrated in step 828 by disassociating their respectivedigital assets entitlements from the unique system identifier of thesource system and then associating it with the unique system identifierof the target system. Then, or if it is determined in step 816 that allinventoried digital assets data and associated digital assetsentitlement data is currently on the digital assets entitlement system,digital assets migration operations may end in step 830.

Although FIG. 8 discloses a particular number of steps to be taken withrespect to method 800, method 800 may be executed with greater or lessersteps than those depicted in FIG. 8. In addition, although FIG. 8discloses a certain order of steps to be taken with respect to method800, the steps comprising method 800 may be completed in any suitableorder.

Method 800 may be implemented using information handling system 100,system 200, components thereof, and/or any other system operable toimplement method 800. In certain embodiments, method 800 may beimplemented partially or fully in software and/or firmware embodied incomputer-readable media.

FIG. 9 illustrates a flow chart of an example method 900 foropportunistic migration of digital assets, in accordance withembodiments of the present disclosure. In accordance with method 900, afile type and/or size and application type and/or size may beidentified, and a mode of data transfer may be selected for migration ofdigital assets from a source information handling system to a targetinformation handling system based on the file type and/or size and/orapplication type and/or size. A “mode of data transfer” may comprise anymechanism to transfer data between a source information handling systemand a target information handling system. Example modes of data transferinclude short-range wireless transmissions (e.g., near-fieldcommunication and Bluetooth), long-range wireless transmissions (e.g.,Wireless Fidelity or “Wi-Fi”), and wired transmissions (e.g., Ethernet).

In some embodiments, one or more portions of method 900 may executecontemporaneously with one or more portions of method 800 describedabove. According to certain embodiments, method 900 may begin at step902. As noted above, teachings of the present disclosure may beimplemented in a variety of configurations of system 200. As such, thepreferred initialization point for method 900 and the order of the steps902-916 comprising method 900 may depend on the implementation chosen.

In method 900, opportunistic digital assets migration operations maybegin in step 902. At step 904, a type and/or size of a digital asset tobe migrated from a source information handling system and targetinformation handling system may be determined.

At step 906, it may be determined whether the size of the digital assetto be migrated is below a first threshold size (e.g., 10 megabytes). Ifthe size of the digital asset is below the first threshold size, method900 may proceed to step 908. Otherwise, method 900 may proceed to step910.

At step 908, responsive to the size of the digital asset being below thefirst threshold size, the digital asset may be transferred via a firstmode of data transfer. In some embodiments, the first mode of datatransfer may comprise data transfer via short-range wirelesstransmissions (e.g., near-field communication and/or Bluetooth). Aftercompletion of step 908, method 900 may proceed to step 916.

At step 910, it may be determined whether the size of the digital assetto be migrated is above the first threshold size and below a secondthreshold size (e.g., one gigabyte). If the size of the digital asset isabove the first threshold size and below the second threshold size,method 900 may proceed to step 912. Otherwise, method 900 may proceed tostep 914.

At step 912, responsive to the size of the digital asset being above thefirst threshold size and below the second threshold size, the digitalasset may be transferred via a second mode of data transfer. In someembodiments, the second mode of data transfer may comprise data transfervia long-range wireless transmissions (e.g., Wireless Fidelity or“Wi-Fi”). After completion of step 912, method 900 may proceed to step916.

At step 914, responsive to the size of the digital asset being above thesecond threshold size, the digital asset may be transferred via a thirdmode of data transfer. In some embodiments, the third mode of datatransfer may comprise data transfer via long-range wirelesstransmissions (e.g., Wireless Fidelity or “Wi-Fi”). After completion ofstep 914, method 900 may proceed to step 916.

At step 916, method 900 may end.

Although FIG. 9 discloses a particular number of steps to be taken withrespect to method 900, method 900 may be executed with greater or lessersteps than those depicted in FIG. 9. In addition, although FIG. 9discloses a certain order of steps to be taken with respect to method900, the steps comprising method 900 may be completed in any suitableorder.

Method 900 may be implemented using information handling system 100,system 200, components thereof, and/or any other system operable toimplement method 900. In certain embodiments, method 900 may beimplemented partially or fully in software and/or firmware embodied incomputer-readable media.

Although method 900 contemplates selection of a mode of data transferbased on a size of a digital asset, in some embodiments, selection of amode of data transfer may be based on a type of digital asset inaddition to or in lieu of selection based on size. For example, in someembodiments, digital assets of a type deemed more critical or of higherpriority may be transferred over a particular mode of data transferwhile digital assets of a type deemed less critical or of lower prioritymay be transferred over another mode of data transfer. As anotherexample, digital assets comprising executable applications may betransferred over a particular mode of data transfer while digital assetscomprising data may be transferred over another mode of data transfer.

The present disclosure is well adapted to attain the advantagesmentioned as well as others inherent therein. While the presentdisclosure has been depicted, described, and is defined by reference toparticular embodiments of the disclosure, such references do not imply alimitation on the disclosure, and no such limitation is to be inferred.The disclosure is capable of considerable modification, alteration, andequivalents in form and function, as will occur to those ordinarilyskilled in the pertinent arts. The depicted and described embodimentsare examples only, and are not exhaustive of the scope of thedisclosure.

For example, the above-discussed embodiments include software modulesthat perform certain tasks. The software modules discussed herein mayinclude script, batch, or other executable files. The software modulesmay be stored on a machine-readable or computer-readable storage mediumsuch as, for example, a disk drive. Storage devices used for storingsoftware modules in accordance with embodiments of the disclosure may bemagnetic floppy disks, hard disks, or optical discs such as CD-ROMs orCD-Rs, for example. A storage device used for storing firmware orhardware modules in accordance with embodiments of the disclosure mayalso include a semiconductor-based memory, which may be permanently,removably or remotely coupled to a microprocessor/memory system. Thus,the modules may be stored within a computer system memory to configurethe computer system to perform the functions of the module. Other newand various types of computer-readable storage media may be used tostore the modules discussed herein. Additionally, those skilled in theart will recognize that the separation of functionality into modules isfor illustrative purposes. Alternative embodiments may merge thefunctionality of multiple modules into a single module or may impose analternate decomposition of functionality of modules. For example, asoftware module for calling sub-modules may be decomposed so that eachsub-module performs its function and passes control directly to anothersub-module.

As used herein, when two or more elements are referred to as “coupled”to one another, such term indicates that such two or more elements arein electronic communication or mechanical communication, as applicable,whether connected indirectly or directly, with or without interveningelements.

This disclosure encompasses all changes, substitutions, variations,alterations, and modifications to the example embodiments herein that aperson having ordinary skill in the art would comprehend. Similarly,where appropriate, the appended claims encompass all changes,substitutions, variations, alterations, and modifications to the exampleembodiments herein that a person having ordinary skill in the art wouldcomprehend. Moreover, reference in the appended claims to an apparatusor system or a component of an apparatus or system being adapted to,arranged to, capable of, configured to, enabled to, operable to, oroperative to perform a particular function encompasses that apparatus,system, or component, whether or not it or that particular function isactivated, turned on, or unlocked, as long as that apparatus, system, orcomponent is so adapted, arranged, capable, configured, enabled,operable, or operative. Accordingly, modifications, additions, oromissions may be made to the systems, apparatuses, and methods describedherein without departing from the scope of the disclosure. For example,the components of the systems and apparatuses may be integrated orseparated. Moreover, the operations of the systems and apparatusesdisclosed herein may be performed by more, fewer, or other componentsand the methods described may include more, fewer, or other steps.Additionally, steps may be performed in any suitable order. As used inthis document, “each” refers to each member of a set or each member of asubset of a set.

Although exemplary embodiments are illustrated in the figures anddescribed below, the principles of the present disclosure may beimplemented using any number of techniques, whether currently known ornot. The present disclosure should in no way be limited to the exemplaryimplementations and techniques illustrated in the drawings and describedabove.

Unless otherwise specifically noted, articles depicted in the drawingsare not necessarily drawn to scale.

All examples and conditional language recited herein are intended forpedagogical objects to aid the reader in understanding the disclosureand the concepts contributed by the inventor to furthering the art, andare construed as being without limitation to such specifically recitedexamples and conditions. Although embodiments of the present disclosurehave been described in detail, it should be understood that variouschanges, substitutions, and alterations could be made hereto withoutdeparting from the spirit and scope of the disclosure.

Although specific advantages have been enumerated above, variousembodiments may include some, none, or all of the enumerated advantages.Additionally, other technical advantages may become readily apparent toone of ordinary skill in the art after review of the foregoing figuresand description.

To aid the Patent Office and any readers of any patent issued on thisapplication in interpreting the claims appended hereto, applicants wishto note that they do not intend any of the appended claims or claimelements to invoke 35 U.S.C. § 112(f) unless the words “means for” or“step for” are explicitly used in the particular claim.

1. An information handling system for migrating digital assets,comprising: a storage medium configured to store information regardingdigital assets to be migrated from a source system to a target system;and a processor configured to: determine a size of a digital asset to bemigrated from the source system to the target system; and select a modeof data transfer from the source system to the target system for thedigital asset based on the size of the digital asset, wherein theselected mode includes transferring data via a particular data transfermethod.
 2. The information handling system of claim 1, wherein theprocessor is further configured to: select a first mode of data transferif the size is below a first threshold size; and select a second mode ofdata transfer if the size is above the first threshold size.
 3. Theinformation handling system of claim 1, wherein the processor is furtherconfigured to: select a first mode of data transfer if the size is belowa first threshold size; select a second mode of data transfer if thesize is above the first threshold size and below a second thresholdsize; and select a third mode of data transfer if the size is above thesecond threshold size.
 4. The information handling system of claim 3,wherein: the first mode of data transfer comprises short-range wirelesstransmissions; the second mode of data transfer comprises long-rangewireless transmissions; and the third mode of data transfer compriseswired transmissions.
 5. The information handling system of claim 1,wherein the processor is further configured to: determine a type of thedigital asset to be migrated from the source system to the targetsystem; and select the mode of data transfer from the source system tothe target system for the digital asset based on the size of the digitalasset and the type of the digital asset.
 6. A computer-implementedmethod for opportunistic migration of digital assets, comprising:determining a size of a digital asset to be migrated from a sourcesystem to a target system; and selecting a mode of data transfer fromthe source system to the target system for the digital asset based onthe size of the digital asset, wherein the selected mode includestransferring data via a particular data transfer method.
 7. The methodof claim 6, further comprising: selecting a first mode of data transferif the size is below a first threshold size; and selecting a second modeof data transfer if the size is above the first threshold size.
 8. Themethod of claim 6, further comprising: selecting a first mode of datatransfer if the size is below a first threshold size; selecting a secondmode of data transfer if the size is above the first threshold size andbelow a second threshold size; and selecting a third mode of datatransfer if the size is above the second threshold size.
 9. The methodof claim 8, wherein: the first mode of data transfer comprisesshort-range wireless transmissions; the second mode of data transfercomprises long-range wireless transmissions; and the third mode of datatransfer comprises wired transmissions.
 10. The method of claim 6,further comprising: determining a type of the digital asset to bemigrated from the source system to the target system; and selecting themode of data transfer from the source system to the target system forthe digital asset based on the size of the digital asset and the type ofthe digital asset.
 11. An article of manufacture comprising: a computerreadable medium; and computer-executable instructions carried on thecomputer readable medium, the instructions readable by a processor, theinstructions, when read and executed, for causing the processor to:determine a size of a digital asset to be migrated from a source systemto a target system; and select a mode of data transfer from the sourcesystem to the target system for the digital asset based on the size ofthe digital asset, wherein the selected mode includes transferring datavia a particular data transfer method.
 12. The article of claim 11, theinstructions for further causing the processor to: select a first modeof data transfer if the size is below a first threshold size; and selecta second mode of data transfer if the size is above the first thresholdsize.
 13. The article of claim 11, the instructions for further causingthe processor to: select a first mode of data transfer if the size isbelow a first threshold size; select a second mode of data transfer ifthe size is above the first threshold size and below a second thresholdsize; and select a third mode of data transfer if the size is above thesecond threshold size.
 14. The article of claim 13, wherein: the firstmode of data transfer comprises short-range wireless transmissions; thesecond mode of data transfer comprises long-range wirelesstransmissions; and the third mode of data transfer comprises wiredtransmissions.
 15. The article of claim 6, the instructions for furthercausing the processor to: determine a type of the digital asset to bemigrated from the source system to the target system; and select themode of data transfer from the source system to the target system forthe digital asset based on the size of the digital asset and the type ofthe digital asset.